About: description of service end-point

This page provides a structured representation (serialized as HTML+RDFa) of the description of the entity denoted ("referred to") by the hyperlink that anchors the About: <Entity Label> text at the top.

The data is presented here in the form of a collection of Entity->Attribute->Value (EAV) or Subject->Predicate->Object (SPO) relations.

In conformance with core Web Architecture, the same description data may also be retrieved in a variety of other negotiable serialization formats, which currently include CSV, HTML+Microdata, (X)HTML+RDFa, N-Triples, Turtle, N3, RDF/JSON, JSON-LD, RDF/XML, Atom, and CXML.

Why is this page important?

This page and its neighbors provide 5-Star Linked Data URIs (Web Super Keys) for HTTP-accessible data. These URIs are powerful starting points for serendipitous data discovery using the Web's "follow your nose" pattern, as well as a key ingredient for SPARQL queries over HTTP, ODBC, JDBC, ADO.NET, OLE-DB, or XMLA connections.

A single link from this page can be the seed of a powerful Web traversal, en route to discovery and exploitation of unimagined insights, using existing tools such as browsers, spreadsheets, business intelligence and analytics packages, basic report writers, presentation generators, project management packages, and many others.

How can I discover more structured data like this?

A variety of discovery pointers are available to users and user agents (software programs) that include:

<link /> relations embedded within the <head /> section of each description page
"Link:" response headers included as part of HTTP response metadata.

Can I expose my own Web resources this way?

Yes! Simply include entries, based on the example below, in the <head/> section of your (X)HTML page, whether static or dynamically generated --

<link rel="related"
    title="My Data in Linked Data form"
    href="http://linkeddata.uriburner.com/about/id/<scheme-part-of-url>/<host-part-of-url>/<path-part-of-url>"
    />

The scheme part is the first bit of a URI, up to but not including the first colon (":"). The host part includes the port, if any, and is found between the double solidus ("//") following the first colon, and the first solidus ("/") thereafter. The path part is everything thereafter (possibly including a query part or fragment identifier part).

For example, if your original page were at --

http://en.wikipedia.org/wiki/Linked_Data

-- the scheme part is "http", the host part is "en.wikipedia.org", and the path part is "wiki/Linked_Data". You could therefore provide access to a Linked Data graph rendition by including a <head/> entry like this --

<link
    rel="related"
    title="Linked data - Wikipedia, the free encyclopedia - in Linked Data form"
    href="http://linkeddata.uriburner.com/about/id/http/en.wikipedia.org/wiki/Linked_Data"
    />

Additional Information

URIBurner.com -- a live service that produces pages like this
OpenLink Data Explorer (ODE) -- a browser plug-in that enables you to browse and bookmark Linked Data pages via additions to the browser menus, both main and contextual
- ODE usage examples

Sponging disallowed (Read-only view)

A description of the service end-point, including its operations, parameters etc.

% meta-cartridges called:

Meta-cartridge [execution time]:

Subject of Relation
Object of Relation

Property	Value
type	ObjectPropertyhttp://www.w3.org/2002/07/owl#ObjectProperty
label	descripción del end-point del servicio (es) description of service end-point (en) descrizione dell'endpoint del servizio (it) popis přístupového bodu služby (cs) endpointbeskrivelse (da)
domain	Data servicehttp://www.w3.org/ns/dcat#DataService
comment	Popis přístupového bodu služby včetně operací, parametrů apod. (cs) Una descripción del end-point del servicio, incluyendo sus operaciones, parámetros, etc. (es) Una descrizione dell'endpoint del servizio, incluse le sue operazioni, parametri, ecc. (it) A description of the service end-point, including its operations, parameters etc. (en) En beskrivelse af det pågældende tjenesteendpoint, inklusiv dets operationer, parametre etc. (da)
described by	proxy:entity/http/www.w3.org/ns/dcathttp://demo.openlinksw.com/about/id/entity/http/www.w3.org/ns/dcat
definition	Popis přístupového bodu služby včetně operací, parametrů apod. (cs) Una descripción del end-point del servicio, incluyendo sus operaciones, parámetros, etc.. (es) Una descrizione dell'endpoint del servizio, incluse le sue operazioni, parametri, ecc. (it) A description of the service end-point, including its operations, parameters etc. (en) En beskrivelse af det pågældende tjenesteendpoint, inklusiv dets operationer, parametre etc. (da)
scope note	Una descrizione dell'endpoint può essere espressa in un formato leggibile dalla macchina, come una descrizione OpenAPI (Swagger), una risposta GetCapabilities OGC, una descrizione del servizio SPARQL, un documento OpenSearch o WSDL, una descrizione API Hydra, o con del testo o qualche altra modalità informale se una rappresentazione formale non è possibile. (it) The endpoint decription gives specific details of the actual endpoint instance, while dct:conformsTo is used to indicate the general standard or specification that the endpoint implements. (en) An endpoint description may be expressed in a machine-readable form, such as an OpenAPI (Swagger) description, an OGC GetCapabilities response, a SPARQL Service Description, an OpenSearch or WSDL document, a Hydra API description, else in text or some other informal mode if a formal representation is not possible. (en) Popis přístupového bodu dává specifické detaily jeho konkrétní instance, zatímco dct:conformsTo indikuje obecný standard či specifikaci kterou přístupový bod implementuje. (cs) Una descripción del endpoint del servicio puede expresarse en un formato que la máquina puede interpretar, tal como una descripción basada en OpenAPI (Swagger), una respuesta OGC GetCapabilities, una descripción de un servicio SPARQL, un documento OpenSearch o WSDL, una descripción con la Hydra API, o en texto u otro modo informal si la representación formal no es posible. (es) La descrizione dell'endpoint fornisce dettagli specifici dell'istanza dell'endpoint reale, mentre dct:conformsTo viene utilizzato per indicare lo standard o le specifiche implementate dall'endpoint. (it) Popis přístupového bodu může být vyjádřen ve strojově čitelné formě, například jako popis OpenAPI (Swagger), odpověď služby OGC getCapabilities, pomocí slovníku SPARQL Service Description, jako OpenSearch či WSDL document, jako popis API dle slovníku Hydra, a nebo textově nebo jiným neformálním způsobem, pokud není možno použít formální reprezentaci. (cs) La descripción del endpoint brinda detalles específicos de la instancia del endpoint, mientras que dct:conformsTo se usa para indicar el estándar general o especificación que implementa el endpoint. (es) Endpointbeskrivelsen giver specifikke oplysninger om den konkrete endpointinstans, mens dct:conformsTo anvendes til at indikere den overordnede standard eller specifikation som endpointet er i overensstemmelse med. (da) The endpoint description gives specific details of the actual endpoint instance, while dct:conformsTo is used to indicate the general standard or specification that the endpoint implements. (en) En beskrivelse af et endpoint kan udtrykkes i et maskinlæsbart format, såsom OpenAPI (Swagger)-beskrivelser, et OGC GetCapabilities svar, en SPARQL tjenestebeskrivelse, en OpenSearch- eller et WSDL-dokument, en Hydra-API-beskrivelse, eller i tekstformat eller i et andet uformelt format, hvis en formel repræsentation ikke er mulig. (da)
change note	New property in DCAT 2.0. (en) Nová vlastnost přidaná ve verzi DCAT 2.0. (cs) Nueva propiedad agregada en DCAT 2.0. (en) Nuova proprietà in DCAT 2.0. (it) Ny egenskab i DCAT 2.0. (da)

Property	Value
topic	The data catalog vocabularyhttp://www.w3.org/ns/dcat